Store Solutions

ABSTRACT

Disclosed are systems and methods that time correlate input at a point of entry of consumer data of least two identifications for products, prescriptions, vouchers, or codes, uses positive correlation determinations for triggering output of predetermined information. The time correlation of identifications may be used to build a time correlation database, and thereafter use that database for targeted communications. Related inventions include an intelligent Y cable or the like to filter data transmitted from a scanner at a point of entry of consumer data, and a novel POS CS configured to receive bar codes that would otherwise cause the POS CS to enter an error condition.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority to provisional application havingattorney docket reference PIP202BESEP-US, application No. 60/943,462,and filing date Jun. 12, 2007, titled “Convenience Store Solutions”. Thedisclosure of 60/943,462 is incorporated herein by reference.

BACKGROUND

ID is an acronym for IDentification.

CID is an acronym for Consumer IDentification. CID means a unique code.Typically, a CID is associated with a particular consumer or a purchasehistory.

CS is an acronym for Computer System.

POS is an acronym for Point Of Sale.

LM is an acronym for Local Marketing.

CM is an acronym for Central Marketing.

I/O is an acronym for Input and Output.

RFID is an acronym for Radio Frequency Identification.

A POS CS is a computerized system including structure for performing atleast the following functions: receiving transaction information at aPOS including item identifier, price, calculating transaction totals,logging POS transactions, and storing a list of store inventory andinventory item prices.

Some POS CSs are designed to sore and utilize standardized manufacturercoupon files. These files for example contain in association with oneanother, coupon identifier, which may appear on a coupon in a bar codeformat, discount amount, and product identification. As a result, aproperly programmed POS CS can validate a coupon received during atransaction (by determining a product associated with the coupon isbeing purchased), and if found valid, discount the transaction by thediscount amount. Some POS CS may not be capable to perform thevalidation step, in which case they automatically apply the discountamount associated with a coupon when the coupon ID is entered into thePOS CS during a transaction. Other POS CSs lack any coupon files and inthese systems the store clerks can manually enter the discountidentified on the coupon, and the coupon identification code. Most POSCSs are designed to receive data from a scanner. However, scanner dataoutput formats and the POS CS data input formats vary between scannermodels and POS CS models.

Use of paper coupons requires a follow on accounting reconciliation stepwherein the paper coupons amounts owed by each debtor coupon sponsor(such as manufacturers) to each coupon creditor (such as retail store inwhich the coupon was redeemed) are determined and payment thereafterimplemented.

Preferably, the POS CS can perform a host of other functions, includingtracking changes in tracking changes in inventory, providing reports onsales and inventory. accounting in transactions for taxes, generatingorders for additional merchandise, transmitting data (reports, logs,inventory, sales, etc.) to a centralized retail chain store server. APOS CS may also be able to perform marketing and security functions.

A convenience store herein means a retail store having floor space of800-5000 square feet, 500 to 2000 Stock Keeping Units (“SKUs”), and thatsells packaged goods.

Convenience stores typically have a POS CS that includes only a singlePOS terminal. A POS terminal is a location where there are devices fordata input and data output, such as a keyboard, a monitor, a printer,and a bar code scanner. Convenience stores each sell on average around amillion dollars of non packaged goods annually. Convenience storetransactions are characterized by relatively low total purchases pertransaction, averaging $5-6 dollars. The majority of convenience storespurchase transactions are paid for using currency (cash). The averagetime a consumer spends waiting in line and completing a transaction in aconvenience store is about one minute. Roughly 50 percent all revenue inconvenience stores derives from tobacco sales, and 17 percent frombeverage sales. The convenience store market is highly fragmented. Evenchain stores such as “7-11” are often franchises in which the franchiserstore control of store equipment and procedures, such as which POS CS touse, is not absolute.

Some stores, such as Subway and Ukrops otter promotions by transmittingthem to cellular telephone numbers of those customers that have askedfor such transmissions.

A convenience store purchase transaction (or purchase transaction, orjust transaction) herein means a single exchange of cash or credit forpurchase of one or more items for sale in a convenience store.

A purchase history means a collection of data for purchase transactions(including for example in each purchase transaction productidentifications and quantities for items of products purchased, and dateof transaction), of plural purchases, in which each transaction is alsoassociated with a CID. A POS CS determines what product identifiers arein a particular purchase transaction by logging an end of transactionsignal. The end of transaction signal, or tender signal, may be a signalin the POS CS the store clerk generated by pressing a key on a keyboardof the POS CS. A consumer's purchase history is a collection of suchdata in association with a unique CID so that the product identifiersand dates of their purchase may be analyzed for subsequent targeting ofcommunications to the customer having that CID when that customer's CIDis subsequently recognized at the POS. See for example U.S. Pat. No.6,795,809 to O'Brien disclosing that concept.

A targeted offer is an offer limited to association with one or morepeople or logical address that meet certain targeting criteria, suchthat certain other people or logical addresses are not associated withthe offer.

A purchase incentive offer is an offer to use a purchase incentive, inorder to receive a benefit associated with the purchase, such as adiscount.

A coupon is a printed purchase incentive offer that specifiesentitlement to a particular benefit, usually a discount, contingent upona particular action, typically purchasing items of one or more specifiedproducts.

A targeted incentive offer is an incentive offer that targeted.

Product information data means data providing information about one ormore products.

Targeting criteria may be purchase of one or more items of a particularproduct, or of plural products, or failure to purchase an items of oneor more products, or any combination of purchase and non purchase ofplural products, during one or more prior visits or a current visit (ortime intervals prior to or concurrent with the current time) to a retailstore or online shopping sessions with a Web site.

A targeted incentive offer may for example offer a discount contingenton future behavior. That behavior may be a consumer in the futurepurchasing another item of a product the consumer is in the process ofpurchasing or has just purchased, or if the consumer in the futurepurchases an item of a product competing with the product the consumeris purchasing or has just purchased. A targeted incentive offer may forexample offer to a consumer a discount for a subsequent purchase of someitem logically heuristically related to products of the consumer's prioror current purchases.

SUMMARY OF THE INVENTION

In their prior tests of systems for automatically providing targetedincentive offers in convenience stores, the inventors observed twoproblems unique to convenience stores. First, substantial couponredemption fraud by store clerks. Second, ineffective services foraccounting for redeemed purchase incentives. Thus, the inventorsrecognized any system for automatically providing targeted incentiveoffers in convenience stores would have to solve these problems. Thesystem and methods described below do that.

In their prior tests and surveys of the market, the inventors recognizedthat convenience stores implemented many different POS CSs and manydifferent versions of the same generic POS CS. As a consequence, theinventors recognized that only systems and methods generic to existinginstalled POS systems installed in convenience stores would beeconomically feasible. The preferred embodiments described below aregeneric to POS CSs installed in convenience stores.

The inventors recognized that there was a high turnover rate of theconvenience store clerks that operate convenience store POS terminals.POS terminals are used by store clerks for entering purchase transactiondata, processing purchase transactions, and redeeming accepted purchaseincentive offers. As a consequence, the inventors recognized that onlysystems and methods requiring minimal training of store clerks would beeconomically feasible. The system and methods described below requireminimal training of store clerks.

The inventors also recognized that product identification of productitems in the form of bar codes on product packaging, and the format foroptical scanners to transmit bar code identifications to a POS CS, werewell known.

OBJECTS OF THE INVENTION

It is a general object to provide hardware, software, and operationalprocedures that facilitate providing targeted product information datato customers of retail stores.

It is a general object to provide hardware, software, and operationalprocedures that facilitate providing and redeeming purchase incentiveothers for purchase of certain products in retail stores while deterringfraud and providing for detection of fraud.

It is a general object of the invention to provide hardware, software,and operational procedures that facilitate providing and redeemingpurchase incentive offers for transactions in retail stores that requireno modification to existing POS CSs in stores.

It is a general object to provide hardware, software, and operationalprocedures whose cost of installation and operational complexity are lowenough so that its benefits outweigh its costs.

It should be noted that the disclosed inventions have utility in anyretail store, not just convenience stores.

These and other objects are provided by systems and methods that timecorrelate input at a point of entry of consumer data of one or moreidentifications with one or more predetermined time periods. Theidentifications may be for products, prescriptions, vouchers, or otheridentification codes. A positive time correlation determination is atleast one step that is required for triggering output of productinformation data, such as marketing material, promotions, or coupons.The triggering may also require determining that the two time correlatedidentifications also have a predetermined association. This processminimizes print or transmission of information to only targetedinformation. It also, in the context of purchase incentive offers,substantially eliminates fraudulent purchase incentive redemption.communications.

These and other objects are provided by systems and methods that usetime of receipt of scanned bar codes and heuristic data indicating whenactual transactions end to reorganize logged scan data into assumedtransaction records, based upon time of receipt, and to use the assumedtransaction data and targeting criteria and rules to determine when andfor whom to provide targeted information such as product information andvouchers. Moreover, the time correlation of identifications may be usedto build a time correlation database, and thereafter use that databaseand targeting criteria for targeting and customizing prospectivecommunications to individuals.

The inventors also disclose use of a Y cable or the like to transmitdata transmitted from a scanner at a point of entry of consumer data toboth a POS CS and a LM CS and an additional scanner included with the LMCS for scanning voucher codes; or an intelligent Y cable or the like tofilter data transmitted from a scanner at a point of entry of consumerdata to a POS CS so that the POS CS does not receive certain scannedvoucher codes. The intelligent Y cable enables use of bar codes to bescanned by the scanner that would otherwise cause the POS CS to enter anerror condition, thereby expanding the data input and outputcapabilities associated with the point of entry of consumer data,without requiring modification to the pre existing POS system, otherthan replacement of the original scanner cable. The inventors alsodisclose alternatives wherein the POS CS is configured to receive andhandle scanned voucher codes without entering and remaining in an errorcondition.

Preferably, LM CS only prints the voucher after it determining that apurchase transaction triggering printing for the voucher is likely tohave ended.

In some embodiments for delivering coupons, the LM CS prints a vouchercontaining a voucher ID code only depending upon receipt of one or moreproduct IDs required to print the voucher.

In a first class of implementations for delivering coupons, the LM CSresponds to receipt of a voucher code, with no additional requirements,by printing a corresponding coupon either immediately or after somespecified or calculated delay time.

In a second class of implementations for delivering coupons, the LM CStime correlates time of receipt of a voucher ID code associated with aproduct ID code, with time of receipt of the associated product ID code,and the LM CS prints a coupon in response thereto only if it receivesboth the voucher ID code and the associated product ID code within atime determined by the LM CS to likely be during one purchasetransaction.

Given the broad nature of the invention, a host of other related novelinventions are disclosed throughout the specification.

A first aspect comprises a method and system for building a timecorrelation history database comprising a targeting CS comprising atleast one targeting CS central processing unit, at least one targetingCS memory, at least one targeting CS input, and at least one targetingCS output;

wherein said at least one targeting CS input is configured to receive atleast personal device addresses and product identifiers; wherein said atleast one targeting CS memory comprises a time correlation log; whereinsaid time correlation log is configured to store time of receipt of eachone of said at least one personal device addresses in association withthe corresponding one of said personal device address, and to store timeof receipt of each one of said product identifiers in association withthe corresponding one of said product identifiers;

wherein said at least one targeting CS memory comprises a timecorrelation history data structure for storing in association with oneanother, at least (1) a personal device address, (2) a personal deviceaddress time of receipt of said personal device address, and (3) one ormore product identifiers each having a product identifier time ofreceipt correlated in time with said personal device address time ofreceipt; and

wherein said targeting CS is configured to process data in said timecorrelation log to populate said time correlation history data structureby determining if time of receipt of a product identifier in said timecorrelation log is within time of receipt a personal device address timeof receipt in said time correlation log.

Aspects depending on the first aspect include: (2) wherein said at leastone targeting CS memory comprises a targeting rules data structurestoring targeting rules for identifying personal device addresses towhich to send targeting signals by applying targeting rules to data insaid time correlation history data structure; wherein said targeting CSis configured to process data in said time correlation history datastructure using a first targeting rule stored in said targeting rulesdata structure to define a first set of targeted personal deviceaddresses selected from personal device addresses stored in said timecorrelation history data structure; and wherein said targeting CS isconfigured to transmit a targeted signal in association with each one ofsaid first set of targeted personal device addresses; (3) wherein saidpersonal device address is a cellular telephone number or an emailaddress; (4) wherein said targeting CS comprises a LM CS and a CM CS anda network connection enabling them to communicate with one another.

A second aspect comprises a method and system, comprising:

a LM CS, said LM CS including; a LM CS central processing unit forprocessing instructions and data; a LM CS memory for storing data; atleast one LM CS input for receiving identification codes; and at leastone LM CS output for outputting identification codes; wherein said LM CSmemory stores data specifying a correlation time;

wherein said LM CS is configured to output product information dataincluding a first product information identification code to said atleast one LM CS output in response to receipt via said at least one LMCS input of a first voucher identification code and a first productidentification code, only if,

said LM CS receives said first voucher identification code via said atleast one LM CS input and said first product identification code viasaid at least one LM CS input within said correlation time of oneanother.

Aspects depending on the second aspect include

(6) wherein said product information data is coupon data; and whereinsaid LM CS is configured to output coupon data including a first couponidentification code to said at least one LM CS output in response toreceipt via said at least one LM CS input of a first voucheridentification code and a first product identification code, only if,said LM CS receives said first voucher identification code via said atleast one LM CS input and said first product identification code viasaid at least one LM CS input within said correlation time of oneanother;

(7) wherein said LM CS configured to output coupon data furthercomprises: said LM CS configured to store in said LM CS memory (1)identification codes received via said at least one LM CS input and (2)their time of receipt via said at least one LM CS input in associationwith one another; and said LM CS configured to respond to receipt of acurrently received identification code received via said at least one LMCS input, by (1) determining whether said currently receivedidentification code is said first voucher identification code, and (2)if said LM CS determines that said currently received identificationcode is said first voucher identification code, determining whether timeof receipt via said at least one LM CS input of said currently receivedidentification code is within said correlation time of a time of receiptvia said at least one LM CS input of said first product identificationcode;

(8) wherein said LM CS configured to store in said LM CS memory (1)identification codes received via said at least one LM CS input and (2)their time of receipt via said at least one LM CS input in associationwith one another, sequenced by time of receipt; and wherein saiddetermining whether time of receipt via said at least one LM CS input ofsaid currently received identification code is within said correlationtime of time of receipt via said at least one LM CS input of said firstproduct identification code comprises: sequentially retrieving basedupon time of receipt, identification codes received via said at leastone LM CS input, determining whether time of receipt associated witheach retrieved identification code is not within a correlation time ofreceipt of said currently received identification code and, whendetermining that time of receipt associated with a retrievedidentification code is not within said correlation time, ceasing saidsequentially retrieving;

(9) wherein said LM CS configured to output coupon data comprises: saidLM CS configured to store in said LM CS memory (1) identification codesreceived via said at least one LM CS input and (2) their time of receiptvia said at least one LM CS input in association with one another; andsaid LM CS configured to respond to receipt of a currently receivedidentification code received via said at least one LM CS input by (1)determining whether said currently received identification code is saidfirst product identification code, and (2) if said LM CS determines thatsaid currently received identification code is said first productidentification code, determining whether time of receipt via said atleast one LM CS input of said currently received identification code iswithin said correlation time of a time of receipt via said at least oneLM CS input of said first voucher identification code;

(10) wherein said LM CS configured to store in said LM CS memory (1)identification codes received via said at least one LM CS input and (2)their time of receipt via said at least one LM CS input in associationwith one another, sequenced by time of receipt; and wherein saiddetermining whether time of receipt via said at least one LM CS input ofsaid currently received identification code is within said correlationtime of time of receipt via said at least one LM CS input of said firstvoucher identification code comprises: sequentially retrieving basedupon time of receipt, identification codes received via said at leastone LM CS input, determining whether time of receipt associated witheach retrieved identification code is not within a correlation time ofreceipt of said currently received identification code and, whendetermining that time of receipt associated with a retrievedidentification code is not within said correlation time, ceasing saidsequentially retrieving;

(11) wherein said LM CS is configured to output, via said at least oneLM CS output, voucher data including a voucher identification code inresponse to said LM CS receiving via said at least one LM CS input avoucher triggering product identification code;

(12) wherein said voucher triggering product identification code is saidfirst product identification code;

(13) wherein said LM CS memory stores a voucher output triggering lookuptable, and said voucher output triggering lookup table stores inassociation with each voucher identification code at least one productidentification code; wherein said LM CS is configured to, in response toreceipt of a received product identification code, look up in saidvoucher triggering lookup table whether said received productidentification code is associated with said first voucher identificationcode, and, if said LM CS determines that said received productidentification code is associated with said first voucher identificationcode, outputting to at least one of said at least one LM CS output,outputted voucher data corresponding to said first voucheridentification code;

(14) wherein said outputted voucher data includes said first voucheridentification code;

(15) wherein said outputted voucher data is stored in a data structurein a certain CS memory of a certain CS in association with said firstvoucher identification code; and wherein said certain CS is configuredto receive via a certain CS input said outputted voucher data inassociation with a transmitting cellular telephone number from whichsaid voucher data corresponding to said first voucher identificationcode was transmitted, and to transmit via a certain CS output to saidtransmitting cellular telephone number said first voucher identificationcode;

(16) further comprising a wireless electronic transmission device havingsaid transmitting cellular telephone number;

(17) wherein said certain CS is said LM CS;

(18) wherein said certain CS is a CM CS including a CM CS centralprocessing unit, a CM CS memory, at least one CM CS input for inputtingdata, and at least one CM CS output for outputting data;

(19) wherein said certain CS is configured to store in association withone another cellular telephone numbers and product identifications in atime correlation history database; and said time correlation historydatabase stores said transmitting cellular telephone number inassociation with product identifications for products having a time ofreceipt in said LM CS within a second correlation time of time ofreceipt via said certain CS input of a telephone transmission from saidtransmitting cellular telephone number;

(20) wherein said time correlation history database also stores inassociation with each product identification a product identificationtime of receipt via said at least one LM CS input or said certain CSinput;

(21) wherein said product identification time of receipt corresponds toone of time of receipt of a cellular telephone signal in said certainCS, time of receipt of a product identification in said LM CS, and timeof receipt of a product identification in said certain CS;

(22) wherein said at least one LM CS input for receiving identificationcodes comprises a scanner for reading bar codes;

(23) further comprising an intelligent data router containing circuitryconfigured to transmit all scanned bar code data scanned by said scannercorresponding to identification codes along a first data communicationpath coupled to said at least one LM CS input and selectivelytransmitting scanned bar code data along a second data communicationpath;

(24) wherein said circuitry blocks transmission of voucheridentification codes along said second data communication path;

(25) wherein said intelligent router forms part of an intelligent Ycable connecting said scanner to said LM CS;

(26) further comprising a POS CS, a first data communication path fromsaid scanner to said at least one LM CS input, and a second datacommunication path from said scanner to an input of said POS CS, andwherein said POS CS is configured so that transmission of data from saidscanner to said input of said POS CS does not result in an errorcondition in said POS CS;

(27) further comprising a POS CS, a first data communication path fromsaid scanner to said at least one LM CS input, and a second datacommunication path from said scanner to an input of said POS CS, andwherein said POS CS is configured so that transmission of a voucheridentification code from said scanner to said input of said POS CSresults in activation of error code in said POS CS that returns said POSCS to a state in which it awaits receipt of another identification codefrom said scanner;

(28) wherein said at least one LM CS input for receiving identificationcodes comprises a key pad having numerals 0 through 9 for enteringvoucher identification codes in decimal format;

(29) wherein said at least one LM CS input for receiving identificationcodes comprises a scanner;

(30) wherein said at least one LM CS output comprises a printer; whereinsaid printer is configured to print a coupon containing a bar codespecifying said first coupon identification code in response to receiptby said printer of coupon data including said first couponidentification code;

(31) wherein said at least one LM CS output comprises at least one of aprinter, a monitor, and a wireless transmitter; and wherein said atleast one of said printer, said monitor; and said wireless transmitterare configured to output at least one of machine and human readableversions of said first coupon identification code;

(32) wherein said coupon data including said first coupon identificationcode output to said at least one LM CS output includes identification ofat least one product for which a coupon having said first couponidentification code can be redeemed; and

(34) wherein said correlation time is between 30 seconds and 2 minutes.

A third aspect comprises a method and system for outputting coupon data,comprising:

a LM CS, said LM CS including; a LM CS central processing unit forprocessing instructions and data; a LM CS memory for storing data; atleast one LM CS input for receiving identification codes; and at leastone LM CS output for outputting identification codes;

a POS CS;

a bar code scanner for scanning bar codes; and

an intelligent data router containing circuitry configured to transmitall scanned bar code data scanned by said bar code scanner correspondingto identification codes along a first data communication path coupled tosaid at least one LM CS input and selectively transmitting scanned barcode data along a second data communication path coupled to said POS CS.

An aspect dependent upon the third aspect is (34) wherein said circuitryblocks transmission of voucher identification codes along said seconddata communication path.

A fourth aspect comprises a method and system for outputting coupondata, comprising:

a LM CS, said LM CS including; a LM CS central processing unit forprocessing instructions and data; a LM CS memory for storing data; atleast one LM CS input for receiving identification codes; and at leastone LM CS output for outputting identification codes;

a POS CS having a POS CS input;

a bar code scanner for scanning bar codes and coupled to said at leastone LM CS input and to said POS CS input;

wherein said LM CS is configured to output coupon data upon receipt fromsaid bar code scanner of voucher identification data; and

wherein said POS CS is configured so that, upon receipt from said barcode scanner of voucher identification, said POS CS either does notenter an error state or executes error handler code the returns said POSCS to a state in which it awaits receipt of another identification codefrom said bar code scanner.

A fifth aspect comprises a method and a system for issuing productinformation data to a customer near an end of a customer transaction,comprising: a targeting CS comprising at least one targeting CS centralprocessing unit, at least one targeting CS memory, at least onetargeting CS input, and at least one targeting CS output; wherein saidat least one targeting CS input is configured to receive productidentifiers of product items being scanned at a POS in a retail store;wherein said at least one targeting CS memory comprises a timecorrelation log; wherein said time correlation log is configured tostore at least (1) time of receipt of each product identifier scanned atsaid POS in association with (2) the corresponding product identifier;wherein said targeting CS memory stores at least one assumed end oftransaction rule for assuming when a customer transaction at said POS isending; wherein said targeting CS is structured to determine from datain said time correlation log and said at least one assumed end oftransaction rule an assumed end of transaction time; and wherein saidsystem is configured to convey to a customer at the POS productinformation data at a time depending upon said assumed end oftransaction time.

Aspects depending upon the fifth aspect include wherein said productinformation data is a voucher ID and said customer transaction is apurchase transaction; wherein said product information data is voucherID, and said system is configured to display the existence of a voucherand to print the voucher containing said voucher ID, either in responseto, or at a specified time after, said assumed end of transaction time;wherein said at least one assumed end of transaction rule comprises afirst time interval; wherein said at least one assumed end oftransaction rule comprises a first time interval and said rule specifiesan assumed end of transaction when said first time interval elapses withno codes received by said at least one targeting CS input; wherein saidat least one assumed end of transaction rule comprises a second timeinterval; wherein said at least one assumed end of transaction rulecomprises association of a set of at least two products IDs received bysaid at least one targeting CS input within said second time interval ofone another; and wherein said targeting CS is structured:

(1) to determine whether product identification data newly received insaid targeting CS is a voucher ID, and if so, automatically retrievingfrom said at least one targeting CS memory at least one associatedproduct identifier associated with said voucher ID, then

(2) to determine whether pre existing records in said time correlationlog have a time of receipt within a first correlation time of time ofreceipt of said voucher ID and include a product identifier that is saidassociated product identifier;

(3) to determine whether product identifiers received after said time ofreceipt of said voucher ID prior to said assumed end of transaction timeare said associated product identifier; and

to print or display to said customer said information data if (1) ispositive and either (2) or (3) is positive.

DETAILED DESCRIPTION OF EMBODIMENTS

These and other objects are provided by the several embodiments ofretail store solutions, preferably convenience store solutions,variations thereon, and methods of use, noted below in connection withthe figures and there after.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a schematic view of network computer system 1;

FIG. 2 is a plan view of the area near a POS of convenience store A ofFIG. 1;

FIG. 3 is a data table view of the data structure Voucher TriggeringTable 300;

FIG. 4 is a data table view of the data structure Coupon TriggeringTable 400;

FIG. 5 is a data table view of the data structure Coupon TriggeringTable 500;

FIG. 6 is a data table view of the data structure Scanning Log Table600;

FIG. 7 is a data table view of the data structure Coupon Print FileLookup Table 700;

FIG. 8 is a data table view of a data structure Output Coupon Data 800;

FIG. 9 is a design view of a portion of Time Correlation HistoryDatabase 900;

FIG. 10 is a high level flow chart showing logical flow of decisions andactions by LM, CS 40.

FIG. 11 shows process flow 1100 for printing vouchers and coupons;

FIG. 12 shows process flow 1200 for printing vouchers and coupons forcertain regulated products; and

FIG. 13 shows software interface diagram 1300 for one embodiment of LMCS 40.

DETAILED DESCRIPTION OF THE FIGURES AND EMBODIMENTS

FIG. 1 shows network CS 1 including CM CS 10, retailer central server CS20, network, T, convenience store A, convenience store B, conveniencestore C, ellipses “ . . . ” indicating an indefinite number ofadditional convenience stores. FIG. 1 shows that in convenience store Athere is POS CS 30, LM CS 40, scanner 50, and intelligent Y cable 60.Although not shown, each of the other convenience stores include theirown POS CS, scanner, Y cable, and LM CS. Lines connecting elements inFIG. 1 indicate data communication paths which each may be wired orwireless.

Each CS herein includes at least a Central Processing Unit (CPU) forprocessing data, a memory for storing data, an in input for receivingdata, and an output for outputting data. Examples of memory include RAM,read writeable compact disks, and magnetic memory media hard drives.Examples of inputs include data communication paths from wirelessreceivers, scanners, numeric keypads, keyboards, computer mouse, touchsensitive screens, and network interfaces. Examples of outputs includedata communication paths to printers, monitors, network interfaces, andwireless transmitters. Reference herein to “configured” to perform aspecified function in connection with CSs and semiconductor logicdevices means either programmed to perform or hard wired to perform thespecified function.

CM CS 10 includes a CM CS CPU, a CM CS memory, at least one CM CS input,and at least one CM CS output. Retailer central CS 20 includes aRetailer central CS CPU, a retailer central CS memory, at least oneretailer central CS input, and at least one retailer central CS output.POS CS 30 includes a POS CS CPU, a POS CS memory, at least one POS CSinput, and at least one POS CS output.

LM CS 40 includes a LM CS CPU, a LM CS memory, at least one LM CS input,and at least one LM CS output. Preferably, LM CS 50 includes a cellulartelephone card enabling it to make cellular telephone calls in order touse the cellular telephone network to communicate with CM CS 10.Alternatively, LM CS 40 may have a NIC card and network cable networkconnection, and/or a WiFi or similar standardized wireless networkconnection. Preferably, LM CS 40 includes a keypad into which customersmay enter codes, such as a sequence of numerals. In addition,preferably, LM CS 40 includes a printer for printing and a display fordisplaying for customers, product information data, targeted signals,vouchers, codes, and coupons and the existence of a voucher or couponbeing printed for the customer. LM CS 40 may have an alphanumericprogrammable LED display facing the consumer. LM CS 40 preferably alsohas a built in bar code scanner (in addition to scanner 50) facing theconsumer and remote from the cashier. The built in bar code scanner andkeypad preferably enable the consumer to scan their voucher codes and/ormanually enter their voucher codes independent of action by the storeclerk and independent of scanner 50. In some embodiments having a builtin bar code scanner and keypad in LM CS 40, customers are instructed toscan their vouchers or enter their voucher codes in LM CS 40's scanneror keypad. In these embodiments, the requirement for an intelligent Ycable, as opposed to a Y cable, to prevent voucher codes from reachingthe POS CS 30 is moot, since bar codes for vouchers would not betransmitted to POS CS 30.

Scanner 50 includes a light source having a specified frequency, amechanism to sweep the light source across one or more paths, one ormore light detectors to detect changes in intensity of light at thespecified frequency and duration of those changes. Scanners that scanone or two dimensional bar codes, and stacks of bar codes, are known inthe art. Scanner 50 is configured to convert scanned information basedupon a predetermined one of plural bar code specifications into a serialdata sequence representing decimal numbers in a predetermined one ofplural logical data formats. Bar code specifications and logical dataformats are well known in the art.

Alternatively, scanner 50 may be, or may include, or there may be inaddition to an optical scanner, an RFID scanner and configured to scanproduct IDs from RFIDs attached to product items brought close to RFIDscanner 50. Reference herein to scanner 50 is intended to cover eitheror both forms of product ID scanners.

Network, I, is a set of computer having logical network addresses andoperating to forward information to addresses associated with eachpacket of transmitted data. Network I may be the Internet or a privatenetwork, or pieces of both.

Intelligent Y cable 60 preferably includes a programmable device forfiltering the serial decimal data transmitted from the scanner. Morepreferably, intelligent Y cable 60 includes a Y cable CS including a Ycable CPU, a Y cable memory, at least one Y cable input, and at leastone Y cable output. Preferably, the Y cable CS has an input coupling toan output of scanner 50 to receive serial decimal data from the scannercorresponding to bar code identifications scanned by scanner 50.Preferably, a first output of the Y cable CS connects to a scanner inputof LM CS 40 to transmit all serial decimal data output from scanner 50to the LM CS 40. Preferably, the Y cable CS has a second outputconnecting to an input to the POS CS 30 to selectively transmit serialdecimal data to an input of POS CS 30. The Y cable CS is preferablyconfigured to block transmission from scanner 50 to POS CS 30 of scandata providing voucher information, including triggered telephone codesand voucher identifications.

In one embodiment, coupon information is electronically transmitted fromLM CS 40 to POS CS 10, thereby mooting the requirement to print a papercoupon. In this embodiment, intelligent Y cable 60 and LM CS 40 areconfigured to provide two way communication, and intelligent Y cable 60is configured to forward coupon identifications it receives from LM CS40 to the scanner input interface of POS CS 30.

Preferably, the intelligent Y cable CS has a configuration input forreceiving configuration information and data from LM CS 30 or anothersource of configuration information. The Y cable CS configurationinformation may provide to the Y cable CS, the data specificationrequired for the Y cable CS to interpret as decimal data, the datatransmitted from scanner 50. The Y cable CS configuration informationmay also specify scanned identifications to not retransmit, or to blocktransmission of, to POS CS 30. That is, the Y cable CS may be configuredto filter out from the data line coupled to POS CS 30 voucher codes asdefined by a voucher code specification. This results in intelligent Ycable 60 blocking all bar codes corresponding to voucher information(including voucher telephone codes and voucher identifications, that is,any code relating to LM CS 40's non coupon outputs to a customer) fromthe communication line coupled to POS CS 30. For example, the Y cable CSmay butter data received from scanner 50, determine its decimal value,and block decimal values whose initial three digits are all zero, if thespecifications are that initial three digits of zero means a voucher ID.For example, such a specification may be for all voucher informationcorresponds to bar codes that begin with “111” or “000” or any othersequence of initial numerals of a bar code not associated withidentifications used to identify products, coupons, or othermiscellaneous identifications that might be used by the particular POSCS 30. Whatever the data specification of the scanner and the voucherinformation, intelligent Y cable is preferably configured to blocktransmission of bar code data corresponding to voucher information fromPOS CS 30. Preferably, intelligent Y cable 60 is configured to transmit(or not block) all bar code information from scanner 50 to LM CS 40.

Typical POS CS 30 includes a POS CS CPU, a POS CS memory, a POS CSkeyboard, a POS CS monitor, a POS CS scanner port to receive a cableconnected to scanner 50, and a printer for printing purchase transactionreceipts. In addition, POS CS memory preferably stores informationincluding a POS CS product information lookup table for looking upproduct information such as price and description based upon receiptfrom scanner 50 of product identifications. Ideally, the POS CS productinformation lookup table contains one product identifications record foreach bar coded product in the store, although it may contain additionalproduct identifications for products not currently in that store.Preferably, POS CS product information lookup table also containsrecords for manufacturer sponsored coupons each including a couponidentifications, a coupon product description, and a discount valueauthorized by tender of a corresponding coupon. Preferably, the POS CSis configured to validate scanned coupons by determining from productdata during the pending transaction whether the discount valueassociated with the coupon is authorized. Preferably, the POS CSincludes an input receiving and interpreting the serial decimal datatransmitted from scanner 50 as product and coupon identifications codes.In the preferred embodiments, scanner 50 and POS CS 30 implemented in aretail store remain unchanged upon addition of LM CS 40.

A typical POS CS in a store owning many companies communicates vianetwork I with retail central CS 20 in order to update itsspecifications of product IDS, coupon IDS, bar code scanner output dataspecifications, and exchange transaction information as is well known inthe art.

FIG. 2 shows a section of a convenience store including the areasurrounding the POS showing preferred positions of the LM CS 30, POS CS40, scanner 50 and the people involved in sales transactions. This areaincludes an area marked “customer location” where the customer normallyis located during a purchase transaction, an area marked “store clerklocation” where the store clerk normally is located during a purchasetransaction, counter top 210, and Y cable line portions 60A, 60B, and60C. Preferably, the I/O devices including keyboards and keypads of POSCS 30 face the store clerk and are out of reach of the customer.Preferably, I/Os of LM CS 40 faces the customer position and is out ofreach of the store clerk when the store clerk is operating POS CS 30.

FIGS. 3-9 specify data structures in LM CS 40 or CM CS 10, in both, orsplit between the two, along with variations to account for CM CS 10storing records for a plurality of LM CSs. FIGS. 3-8 are data tableviews. FIG. 9 is a design view.

A data table view is a view of logical associations between data storedin a database management system. A design views show field names andassociations between fields in different tables in a manner well knownin the database art.

Data tables referred to herein contain fields each of which has anassociation field name, and records each of which has one data cell foreach of the data fields. Data in data cells in the same record areassociated with one another by virtue of the common identifications ofthe record in which they are stored.

Fields in distinct tables may be linked, which means that common valuesin those fields define an association of the corresponding records inthose distinct tables. One to one, one to many, and many to many links,as those terms are used in the field of database management, are wellknown in the art of database management and Structured Query Languageprogramming.

The particular values and relationships of values and digits presentedin the following tables are merely exemplary in order to explain onemode of operation relying upon relationships between data fields in someof the tables. In addition, in these tables, the base representation andnumber of digits are merely exemplary; any number of digits and any baserepresentation are feasible. Moreover, table herein also refers to flatfiles, such as text files, since it is well known that flat files withidentified relationships between the data they store may be used insubstitution for relational database files or tables and links.

Referring to FIG. 3 and the other figures for tables, data values inthose tables are used throughout the following descriptions to explainoperation of novel inventive methods. However, those values and thespecification of data format for each field in each table are onlyexemplary for explaining novel methods. For that purpose, in FIG. 3,triggering product identifications are represented as 6 decimal digits,triggered voucher IDs as 9 decimal digits, and triggered vouchertelephone codes as 4 decimal digits. Data in cells of Triggered VoucherID field 320 includes an initial three digits “111” followed by the samedata appearing in cells in the same record in Triggering Product IDfield 310. Data in cells of Triggered Voucher Telephone Code field 330has the same value as the fourth, fifth, sixth, and eighth decimals inthe cell for the same record in the Triggered Voucher ID field 320.

FIG. 3 show a data table view of a Voucher Triggering table 300containing triggering product ID field 310, triggered Voucher ID field320, and Triggered Telephone Code field 330. FIG. 3 shows exemplaryvalues for data records 340 to 380.

In operation, triggering product IDs are values input into the LM CSthat trigger output by the LM CS of triggered voucher IDs and/ortriggered telephone codes. Triggered telephone codes are codes acustomer can submit by texting them on their personal device such astheir cellular telephone, during a telephone call to a specifiedtelephone number. The specified telephone number and instructions fortexting are preferably provided to a customer in writing and/or on amonitor by LM CS 40 or CM CS 10 in response receipt of the correspondingtriggering product ID. A result of such texting is a reply containing areturn telephone code, as discussed in connection with subsequentfigures. Both the triggered voucher IDs and the return telephone codesare voucher codes as used herein.

A cellular telephone is one form of a personal device, that is, it has alogical address (cellular telephone number), and it is small enough andlight enough to be carried from place to place, and it can communicatevia a network with other devices. A CS receiving a triggered telephonecode from the personal device responds by (1) identifying thetransmitting personal device number (logical address) and (2)transmitting a return telephone code as a text message to the logicaladdress of the personal device (cellular telephone). The triggeredvoucher ID or the return telephone code (see return telephone code field510 of FIG. 5) may there after be submitted by the customer for inputinto the LM CS 40.

In one alternative, Voucher Triggering table 300 also includes fieldsfor a store ID. In one alternative, Voucher Triggering table 300 alsoincludes a field for POS ID (also called checkout station or checkoutlane ID) such as when the store has plural POSs and possible plural LMCSs, one at each POS. In one alternative, Voucher Triggering table 300also includes a field for LM CS ID such as when plural LM CSs exist inone retail store.

Voucher Triggering Table 300 is preferably stored in LM CS 40 memory foruse by LM CS 40 in determining when to output vouchers and vouchertelephone codes and which such codes to output. Voucher Triggering Table300 may also be stored in CM CS 10 for one retail store, or for aplurality of retail stores in association with the retail store ID.

In some embodiments, LM CS 40 outputs a voucher code only depending uponto receipt therein of a triggering product ID. In one such alternative,LM CS 40 outputs a voucher code in response to receipt therein of atriggering product ID. In one such alternative, LM CS 40 outputs avoucher code in response to receipt therein of a triggering product IDonly if LM CS 40 has not received that triggering product ID within apredetermined time corresponding about to an average purchasetransaction time, or if LM CS 40 has not triggered the same voucher codewithin a predetermined time corresponding to that average purchasetransaction time. In one such alternative, LM CS 40 outputs a triggeredvoucher code only after making a determination that an end oftransaction has likely occurred. The goal of voucher output time is tooutput the voucher after the current transaction has ended but while thecustomer of that transaction is still at the POS and likely to receiveprinted or displayed voucher information.

LM CS 40 may assume an end of transaction has occurred after apredetermined time interval has elapsed during which LM CS 40 receivedno codes from scanner 50. For example, 10 seconds, 15 seconds, 20seconds, or 30 seconds. The predetermined time interval may vary fromstore to store, and it may or may not be based upon analysis of time ofreceipt of scanned codes from that or other stores. LM CS 40 may assumean end of transaction has occurred after receiving a predeterminedsequence of bar codes, or after receiving a predetermined set of barcodes within a time window. For example upon receiving scan codes for asandwich and a drink, indicating a meal purchase, within 15 seconds ofone another, may trigger analysis and printing of any resultingtriggered vouchers and triggered telephone codes. LM CS 40 may alsoimpose a predetermined delay on printing vouchers after determining toprint a voucher, in order to result in the voucher more likely beingprinted after an actual end of transaction, so that the customer cannotprint a resulting coupon and use that resulting coupon in the sametransaction. In this first class of alternatives, subsequent submissionby the customer of the voucher code (either by scanning, manually keyingin, or even telephone transmission) into the LM CS 40 results in LM CS40 printing of a corresponding coupon.

In the first class of alternatives for printing coupons, the coupon isprinted in response to receipt by LM CS 40 of a voucher ID code forwhich there is an associated product ID. In such alternatives, there isneed for table 400 to include product ID field 420 and in table 500 toinclude product ID field 520. This is because, in the first class ofalternatives, receipt by LM CS 40 of an input voucher ID in field 410results in LM CS 40 retrieving the corresponding coupon ID in CouponData 1 field 430, and receipt by LM CS 40 of a return telephone code inReturn Telephone Code field 510 results in LM CS 40 retrieving thecorresponding coupon ID in Coupon Data 2 field 530. Once LM CS 40retrieves the coupon ID, that action eventually results in eitherproviding the coupon to the customer or providing the benefit ordiscount associated with the coupon to the customer.

FIGS. 4-6 are now discussed in connection with the second class ofalternatives for providing coupons.

In a second class of alternatives, printing of a corresponding coupon byLM CS 40 is conditioned upon receipt of both the voucher code and acorresponding product bar code (purchase of which provides entitlementof the holder of the coupon to the value of the coupon) within a timewindow of one another. The time window may initially be set tocorrespond approximately to the length of a purchase transaction in thecorresponding store. For example, 30 seconds, 1 minute, 1 and ½ minutes,or 2 minutes. LM CS 40 may be programmed to truncate the window uponotherwise determining that and end of transaction has occurred, such asdue to a predetermine delay in receiving another code from scanner 50,or scanning of a set of product items in a predetermined amount of timealso indicating a complete transaction, as noted above. LM CS 40 mayprint coupons resulting from its receipt of both a voucher code andcorresponding product ID code or codes, for use by the customer in theongoing transaction, as it identifies such coupons upon receivingproduct ID codes, at an assumed end of transaction, or at apredetermined time after an assumed end of transaction. This secondclass of alternatives and its time correlation requirements arediscussed with respect to some of the following tables.

FIG. 4 shows a data table view of Coupon Triggering Table 400. CouponTriggering Table 400 includes Input VoucherID field 410, Product IDfield 420, and Coupon Data 1 field 430. FIG. 4 also shows exemplary datarecords 440-447. FIG. 4 also shows ellipses below record 447 indicatingthe presence optionally of additional records.

In the first class of alternatives, table 400 need only include Inputvoucher ID field 410 and Coupon Data 1 field 430. Receipt by LM CS 40 ofa voucher code ID prompts LM CS 40 to look up the code in field 410 andretrieve the corresponding coupon data from Coupon Data 1 field 430.

In the second class of alternatives, an input Voucher ID value inputinto LM CS 40 within a correlation time of a Product ID value in thesame record in Coupon Triggering Table 400 triggers output by LM CS 40of the value in Coupon Data 1 field 440 of the same record. Outputtingthe coupon only if an associated product ID is scanned, limits coupongeneration to presumably the same purchase transactions in which boththe voucher ID code and the associated product ID code are received inLM CS 40, thereby reducing coupon fraud and also providing presumedredemption data (print by LM CS 40 and receipt of scan of coupon ID codefrom scanner 50 by LM CS 40) to LM CS 40.

Coupon Triggering Table 400 is preferably stored in LM CS 40 memory foruse by LM CS 40 in determining when to output coupon data. CouponTriggering Table 400 may also be stored in CM CS 10 for one retailstore, or for a plurality of retail stores in which case each recordalso includes an association to at least one retail store ID specifyingthe retail store or stores in which the input voucher ID is valid.

For purposes of example, Input Voucher ID field 410 values arerepresented as 8 decimal digits, included an initial “111”; Product IDfield 430 values are represented as 6 decimal digits; and Coupon data 1field 440 values are represented as 4 decimal digits. The four digits inthe Coupon data 1 field 440 correlate for example to the digits 4-6 and8 in the Input Voucher ID field 401, and to the digits 4-6 and 8 in theTriggered Voucher ID field 320. While not essential, correlation ofdigits in Coupon Data 1 field 430 with digits in fields specifying thecorresponding voucher facilitate tracking of triggered Voucher ID tooutput of coupon data.

Values in Coupon Data 1 field 430 preferably identify either coupon dataor a coupon data record address storing coupon data. Coupon datapreferably contains a coupon identifications represented in a preexisting coupon specification. For example, there is a standardmanufacturers packaged goods coupon specification used to identifyproducts, product purchase requirements (validation), and value ofdiscount associated with each coupon in that specification.

The coupon data may store a value corresponding to the couponidentification, or it may store data resulting in a print (such as aprint file) which when printed contains a machine readable version ofthe coupon identifications, such as a bar code in a conventional barcode specification. Many bar code specification for representing forexample sequences of decimal data are well known.

Preferably, there is a one to one correspondence of Input Voucher IDfield 410 value to Coupon Data 1 field value. As a result, input into LMCS 40 of an input voucher ID within a correlation time previouslyspecified in LM CS 40 of a corresponding product ID will result inoutput by LM CS 40 of a determined coupon data.

In operation relating to triggering products and an input voucher,scanner 50 scans products, and the scanned product IDs are input into LMCS 40. If LM CS 40 determines that any such product ID is a triggeringproduct ID in field 310 of table 300, LM CS 40 responds by outputtingthe corresponding triggering voucher ID in field 320. This output iscommunicated to the customer at the POS whose product items that personis in the process of purchasing are being scanned. Preferably,communication is via a printout of a voucher by a printer of the LM CS40 adjacent the customer at the customer location shown in FIG. 2. Thevoucher preferably includes text specifying one or more products andexplaining that the customer can have the voucher scanned and receive adiscount when the customer purchases one (or more than one) of thoseproducts or some other specified product.

Thereafter, the customer presents the voucher during the same or asubsequent purchase transaction. The bar code scanner scans a bar codeon the voucher encoding the voucher ID. LM CS 40 receives the voucher IDand determines whether that voucher ID appears in one or more record inInput Voucher ID field 410. If so LM CS 40 determines whether itreceives an input within a correlation time of a product having a valuein the corresponding Product ID field 420 of any of the records havingthe voucher ID. If so, LM CS 40 responds by outputting the coupon datain the Coupon Data 1 field for that record. Preferably, the outputtedcoupon data results in LM CS 40 printing the corresponding coupon in theLM CS 40 printer adjacent the customer location shown in FIG. 2.Preferably, LM CS 40 also terminates processing looking for matches forthe input voucher ID either upon finding a match or upon expiration ofthe correlation time from time of receipt associated with the inputvoucher ID.

Thereafter, the customer presents the printed coupon during the same ora subsequent transaction at a POS. Preferably, the coupon is thenscanned by scanner 50, and POS CS 30 preferably recognizes the scannedcoupon identifications, automatically validates the coupon againstpurchase of a qualifying product, and provides a specified coupondiscount to the purchase transaction total if a qualifying product isbeing purchased. LM CS 40 preferably also receives an input from scanner50 containing the coupon identifications.

FIG. 5 shows Coupon Triggering Table 500 including Return Telephone Codefield 510, Product ID field 520, and Coupon Data 2 field 530. FIG. 5also shows exemplary data records 540-547. FIG. 5 also shows ellipsesbelow record 547 indicating the presence optionally of additionalrecords. Note that Return Telephone code field 510 contains voucher IDs.

In operation, a customer inputs a return telephone code to LM CS 40. Thecustomer may enter the return telephone code via a keypad of LM CS 40.The customer may text the telephone code to a cellular telephone numberassociated with LM CS 40. The customer may otherwise wirelessly transmitfrom the customer's wireless transmission personal device the returntelephone code to LM CS 40 or to CM CS 40 for immediate retransmissionto LM CS 40. Upon input by the customer of a return telephone code intoLM CS 40, LM CS 40 determines whether that return telephone codecorresponds to values in one or more records in Return Telephone Codefield 510. If so, LM CS 40 determines whether a product ID scannedwithin a correlation time of input of that return telephone code isreceived from scanner 50. Upon making such a determination, LM CS 40outputs the corresponding coupon data in Coupon Data 2 field 530. Outputof coupon data from table 500 is identical to output of coupon data fromtable 400.

In one alternative, LM CS 40 also includes in the printing of a coupon,printed data identifying any one or more of time of printing;identification of LM CS 40; checkout lane; store location;identification of retail store; and, if printing is based upon coupondata in Coupon Data 2 field 530, data uniquely related to the address ofthe personal device used to obtain the return telephone code. Suchadditional information is useful for security purposes to identify andprevent paper coupon redemption and clearinghouse accounting fraud.

Transmission by a customer using a cellular telephone or otheridentifiable personal wireless device, of triggered telephone code to LMCS 40 or CM CS 10, and data transmission between LM CS 40 and CM CS 10,allows the receiving CS to determine those product IDs scanned within adefined time correlation (such as 30 seconds) with the cellulartelephone number (or like ID) transmission, and to transmit back to thepersonal wireless device of the customer a return telephone code that isunique to that personal wireless device, based upon the telephone numberof logical address of the device or cellular telephone. The timecorrelation association of the cellular telephone number with scannedproduct identifications and POS (store ID, LM CS ID, lane ID or anycombination thereof), and the time correlation of the input of returntelephone codes, which are in turn associated with the cellulartelephone number, with scanned product identifications, enables LM CS 40or CM CS 10 or both to generate a time correlation database ofpresumptively purchased product identifications in association with thecellular telephone number and date of purchase. That enables the CS toperform additional targeted marketing using a time correlation based setof records corresponding to a conventional purchase history databasestructure. This more targeted marketing includes customizing couponoffers to customers to promote certain behavior, such as preferentialpurchase of one manufacturers products in a particular product categoryover time, purchase of products in a different category from those thecustomer has recently purchased, etc. Once the time correlation historydatabase is established with presumptive purchase transaction recordsassociated with cellular telephone number (or personal device logicaladdress) with a particular person, all of the strategies for targetedmarketing employed for purchase history based targeting may be applied.Algorithms for performing the targeting and determining what coupon datato associate with a cellular telephone number, value of resultingcoupons, etc, and targeting criteria for those algorithms to apply indata processing may performed and stored in memory on LM CS 40 or CM CS10. LM CS 40 and CM CS 10 may transmit logged data, targeting data, barcode scanner specifications, and coupon specifications back and forth asnecessary to implement various alternatives depending upon wheretargeting occurs and for updating system data.

In the exemplary data shown in FIG. 5, data in cells of Return TelephoneCode field 510 are shown beginning with “XXXXX”. This represents adecimal 5 digits that encode uniquely, at least uniquely in relation tothe particular store and LM CS 40, cellular telephone number (orinterchangeably logical address) to which a return telephone code istransmitted in response to receipt from that cellular telephone numberof a triggering telephone code appearing in field 330. The number ofdigits encoding cellular telephone number is only exemplary, more orfewer digits may be used. The final four decimal digits of ReturnTelephone Code field 510 preferably correspond to a triggered voucher IDfrom field 320 associated with the triggered telephone code of field 330resulting in the subject return telephone code. The product IDs andassociated coupon data in fields 520 and 530 result from application oftargeting criteria and rules to the time correlation productidentifications history data associated with the cellular telephonenumber associated with the return telephone code.

FIGS. 6 and 7 explain a process in LM CS 40 or CM CS 50 for determiningtime correlations.

FIG. 6 shows a data table view of Scanning Log Table 600. Scanning LogTable 600 is stored in LM CS 40, or in both LM CS 40 and CM CS 10.Scanning Log Table 600 includes Record field 605, Time of Receipt field610 and Identification field 620. FIG. 6 also shows time window 660defined by +50 seconds marker 650 and −45 seconds marker 640 from recordpointer 650. Different plus and minus marker times indicate that theremay be different correlation time window between time subsequent to andtime prior to a record under examination. Record field 605 stores arecord ID which is preferably sequentially incremented as records arecreated for identifications newly input into LM CS 40. Exemplary record3008 at pointer 650 has identifications code value 11112302. Record3014, which is within the +50 second marker 630 of pointer 650, hasidentifications 123457. These values appear in record 444 in table 400and therefore will result in output of corresponding coupon data via theprocess explained below.

Referring to table 600, a process relating to the second class ofimplementations for providing coupons follows. Assume time is 4:00:00and LM CS 40 has just logged record 3008. In response to the new record,LM CS 40 (or alternatively CM CS 10 assuming it has quick access to datarecords accruing in LM CS 40) initiates control process 1000 asdescribed below.

Step 1—In control process 1000, LM CS 40 first determines if the mostrecently generated record 3008 contains a voucher identification, thatis, a value stored in any record in Input Voucher ID field 410 or ReturnTelephone Code field 510. Both those fields contain voucheridentifications that may trigger the output by LM CS 40 of coupon data.It does this by one of two methods. LM CS 40 CPU may retrieve valuesstored in those fields and compare them to the value of theidentifications in record 3008. However, that method is inefficient. Ina more efficient method, all voucher identifications are encoded withcertain digits having specified values, as a filter test value, such asthe first three digits being “111” as in input voucher ID field 410'svalues. In this more efficient method, LM CS 50 CPU compares thespecified digits to the filter test value and determines a voucheridentifications is present when the digits match the filter test valuedigit values. In another alternative, LM CS 50 CPU uses a specificationrelying upon different number of digits for voucher identifications andproduct identifications.

Step 2—In control process 1000, when LM CS CPU determines no voucheridentifications is present, it check for the existence of a new recordin table 600. If no such record is present, it enters a wait state for adetermined number of clock cycles, and periodically checks again,repeating step 1 until the time of 50 seconds shown as the advance timewindow marker 630, expires.

Step 3—When LM CS 40 CPU determines a voucher identifications is present(as in record 3008 because for example it has a filter test value“111”), it first performs analysis of past time records. It nextdetermines those records in table 600 with time values within the pasttime correlation value, which in this example is 45 seconds, asindicated by past time window marker 660. It does this by performing aloop sequentially decrementing by one, the record 605 value, retrievingthat new record, and then comparing the newly retrieved record time ofreceipt to record 3008's time of receipt field 610 value.

Upon reaching a record in which the time difference for times of receiptexceed the past time correlation time, this loop terminates.Concurrently with determinations that time is less than the past timecorrelation time, or thereafter, LM CS 40 CPU retrieves identificationsfrom the corresponding record in table 500. It then sequentiallyretrieves records in tables 300 and 400 that have the product IDspecified in record 3008 (11112302), retrieves the Product ID associatedwith each such record, and compares that product ID to the values forproduct IDs in the records in Scanning Log Table 600 whose time ofreceipt has been determined to be within the 45 seconds past timecorrelation time. If a match occurs, LM CS 40 CPU retrieves the coupondata from the corresponding Coupon Data 1 or Coupon Data 2 field of thecorresponding record for which the match was identified in either table400 or table 500.

Step 4—LM CS 40 CPU then preferably outputs the retrieved Coupon dataand stores a record of the output coupon data and time of output of thecoupon data and other data, in table 700. Alternatively, LM CS 40 storesthe retrieved coupon data until its process steps relating to record3008 are complete, for example storing this data in table 700. In eithercase, LM CS 40 preferably compares stored coupon data retrieved inresponse to processing record 3008 and limits its output to only oneinstance of any coupon data to avoid presenting the consumer withduplicates of the same coupon incentive offer. This limiting stepinvolves an additional sequence or loop of comparisons of coupon dataretrieved in response to processing record 3008. This step alsosubstantially reduces the prospect of bulk fraudulent coupon redemptionby limiting the frequent of production of coupons resulting from aparticular voucher identification.

Step 5—An interesting aspect of time correlation is forward timecorrelation. Processing relating to record 3008 continues for a futuretime correlation time after time of receipt of record 3008, such as 50seconds, as indicated by pointer 530. The past and future portions oftime window 560 relative to a record may be asymmetric. In any case, LMCS 40 may compare either time of newly generated records, or a systemtime, to time of record 3008, and continue comparing identifications infield 520 in the manner specified for past identifications to determinecoupon data to output in relation to record 3008 until time of the mostnewly generated record is more than the future time correlation time, 50seconds, and then cease comparing.

As with the past time correlation steps, LM CS 40 CPU may log theretrieved coupon data, and output the retrieved coupon data to table700, and filter before outputting the coupon data to avoid duplicateoutputs. See the description of tables 700 and 800 in FIGS. 7 and 8 forprocessing of logged retrieved coupon data not yet sent to a printer orotherwise for presentation to the customer.

Future time correlation also requires newly received records beprocessed in the manner specified for record 3008 when record 3008 wasthe newest record. This is preferably performed by parallel processing.A most effective way for LM CS 40 to implement this is, in a step 4.5after step 4 and before step 5.

Comparison of the data values in Table 600 shows that record 3014 iswithin the time correlation window of record 3008 and has anidentifications for a product that is in a record in tables 400 or 500with the voucher identifications of record 3008, specifically record 444of table 400, which has the coupon data value “1232”. Thus, processingof record 3008 in this example results in output of coupon data 1232.

Step 4.5—LM CS 40 CPU increments record value (from 3008 to 3009) andinitiates a new instance of control process 1000.

Thus, as soon as LM CS 40 CPU has finished processing of records in thepast time correlation time window for each record in table 600, itstarts a new instance of the control process which starts processing ofthe past records within the past time correlation time window of thetime of receipt of the new record in file 600, for that new record. Thatmechanism effectively uses processor cycles because it minimizes clockcycles wasted in step 2 in the wait state.

It should be emphasized that the LM CS 40 of CM CS 50 performs theforegoing operations by storing to memory input data, looking up inmemory for use by a CPU the retrieved data for comparisons, additions,subtractions, and decisional steps, and instructing peripheral devices,such as outputs, to output data in predetermined formats compatible withoutput devices.

FIG. 7 shows Coupon Print File Lookup table 700 including CouponIdentifications field 710 and Coupon Print File field 720. CouponIdentifications field 710 for example contains values stored as coupondata in Coupon Data 1 field 430 and Coupon Data 2 field 530. In theforegoing example, output of coupon data 1232 results in LM CS CPU or aprinter peripheral processor retrieving the print file name associatedwith coupon identifications 1232 from table 700, which is printer filename 1232.prt. In the preferred embodiment, LM CS would be configured toprint that file to a printer adjacent the customer's location at thePOS. The file 1232.prt would include in it the image of a bar coderepresenting a coupon, such as a manufacturer's coupon for a product, ina conventional format, for scanning by scanner 50.

Note that print file 1232.prt is correlated via the data associations inthe foregoing tables back to record 350 in table 300, record 444 intable 400, record 544 in table 500. Thus, a resulting coupon orinstructions for its printing are correlated amongst the data tableswith voucher triggering data, voucher data, coupon data, and resultingcoupon.

FIG. 8 shows Output Coupon Data table 800 including Coupon ID field 810;Voucher ID or Return Telephone Code ID field 820; Product ID field 830;Time of Receipt field 840; Final Output Time field 850; Final OutputFlag field 860; and Final Output Status field 870. A recordcorresponding to the example discussed above is 880. Coupon ID field 810contains the coupon identification output by LM CS 40 CPU. Voucher ID orReturn Telephone Code ID field 820 contains the data value from field620 resulting in output the coupon data in field 810. Product ID field830 contains the product ID found to meet time correlation criteria tothe data value in field 820 resulting in output the coupon data in field810. Time of Receipt field 840 contains the corresponding time ofreceipt from table 600. Final Output Time field 850 contains a time atwhich LM CS CPU or a peripheral processor retrieves from table 700 thecorresponding coupon print file and instructs a printer to print thatfile. In some records, records for which LM CS CPU or a peripheralprocessor does not retrieve data from table 700, Final Output Time field850 may contain a null value or a default value.

Final Output Flag field 860 contains a logical value indicating whetherthe corresponding record was processed to determine whether to look up acoupon print file in table 700. Final Output Status field 870 contains alogical value indicating whether the data in Coupon ID field 810 wasused to look up a coupon print file in table 700.

In operation, LM CS 40 CPU outputs to table 800. LM CS CPU (or aperipheral processor) then implements control process 2000 to determinewhether to output print or otherwise convey to a customer couponinformation corresponding to the coupon ID stored in Coupon ID field810. Generally speaking, LM CS 40 CPU uses table 800 to filter out andnot send coupon information to customers for two records havingidentical coupon IDs in Coupon ID field 810 within a third correlationtime of one another. This is performed for example by post processingstep 6.

Step 6—In control process 2000, LM CS 40 CPU preferably retrieves frommemory a third correlation time. LM CS 40 CPU retrieves from table 800the data for the most recent record, in this example, record 880. Itthen sequentially retrieves the data for previous records and determinestime difference between the value for Time of Receipt field 840. If thattime is less than the third correlation time, for example 30 seconds, itdetermines if the value for the Final Output Status is “Y” for yes,meaning that the previous record had previously been processed todetermine to convey its corresponding coupon information to thecustomer, and whether Final Output Flag of the earlier record is “Y” foryes, meaning that the coupon data for that record was retrieved fromtable 700 and conveyed to the customer. If those conditions are met, itdetermines if the values for the Coupon ID field for both records arenot identical. If so, it enters the current system time in the FinalOutput Time field 860, sets the Final Output Flag field 860 value to “Y”for yes, indicating that the data in Coupon ID field 810 is being usedto look up and convey coupon information to the customer, and sets FinalOutput Status field 870 to “Y” meaning that processing to determinewhether to convey corresponding coupon information to the customer forthis record was completed. In addition, LM CS CPU 40 or the associatedprocessor implements the step of retrieving from table 700 the couponprint file corresponding to the value of Coupon ID field 810 in table800, and instructs printing or otherwise Outputting of that coupon file.If any of the foregoing conditions is negative, LM CS 40 CPU sets thevalues for Final Output Flag field 860 and Final Output Status field 870to “N” for no. Upon instructing printing or determining not to printbased upon the current record, such as record 840, control process 2000enters queries table 800 for a newer record than record 870. If no newrecord exists, control process 2000 enters a wait state and repeats thequery.

FIG. 9 shows Time Correlation History Database 900 including designviews of Time Correlation Table 910, Criteria Table 920, and TargetingTable 930. Database 900 is used for targeting of information, such asproduct information and coupons. An underlying assumption is thatproduct items scanned within a correlation time of scanning, or someother indicia of product items in the same purchase transaction, of avoucher associated with a logical address such as a cellular telephonenumber, are for products purchased by the customer using thecorresponding cellular telephone. Table 910 is generated in view of thatassumption by executing code on either LM CS 40 or CM CS 10 designed toassume which product IDs were purchased in a purchase transaction by aparticular customer. It does so using one or more correlation timesand/or product ID association rules to generate records of assumedpurchase transactions.

Time Correlation table 910 contains fields Cell# 911; Return TelephoneCode (510) 912; RS ID (retail store ID) 913; Time A field (time field);and a plurality of product ID fields 915. Cell# field contains thecellular telephone number or logical address associated with returntelephone code (510). RS ID field 913 contains an identifications of theretail store or retail store and checkout lane (based uponidentifications of adjacent LM CS) in which triggering telephone code(330) was printed. Time A field 914 contains a time associated withreceipt of Return Telephone Code (510) field 912. Product ID fields 915contain product identifications associated by time correlation with TimeA.

In operation respecting generation of table 910, the acting CSdetermines all product identifications scanned within a time correlation(or future time and past time correlations) of when a return telephonecode was scanned, and stores those product identifications inassociation with the cellular telephone number, return telephone code,and time of scanning of the return telephone code, in a record in table910. Repeated processing of all scanning log data results in records intime correlation table 910 that appear formally to be records forpurchase transactions in the corresponding retail store.

Criteria Table 920 is only exemplary of a targeting criteria table.Criteria Table 920 contains fields for “Product ID I” in field 921; TimeI in field 922; “Product ID J” in field 923; Time J in field 924; and“Coupon ID X” in field 925. Targeting Table 930 contains results oftargeting applying criteria specified by table 920 to data contained intable 910. Targeting Table 930 contains fields for cellular telephonenumber, cell#; return telephone code (510); RS ID); and coupon ID (530).Lines 926, 927 between fields in tables 910, 920, and 930 indicateassociations or database links of fields containing similar informationin different tables.

Criteria Table 920 contains exemplary criteria for processing data inrecords in Time Correlation Table 910 in order to associate coupon IDs(or coupon data, or marketing data generally, or resulting targetedcommunication generally) with cellular telephone numbers or logicaldevice addresses for subsequent presentation to the customer of atargeted information, optionally via printing of a triggered telephonecode. Optionally, the triggered telephone code also encodes thecustomer's cellular telephone number.

In operation, the processing CS determines whether transaction recordsfor a cellular telephone number in table 910 satisfy criteria specifiedin table 920. More specifically, the processing CS determines if, fromrecords in table 910 that have the same cellular telephone number, thereis one record that has the value for “product ID I” within a fourthcorrelation time of time I and another record that has “product ID J”within a fifth correlation of time J. If so, the processing CS stores arecord in table 930, including generating a return telephone codeencoding the cellular telephone number. Data in targeting table 930 isused by the targeting CS (LM CS 40 or CM CS 10) to recognize a scannedor otherwise entered return telephone code for providing the customerwith a coupon based upon the associated coupon data in the mannerdescribed herein above.

FIG. 10 shows a high level process flow chart 1000 of process flow in LMCS 40, in CM CS 10, or distributed between them, for performing the highlevel processing steps of a certain embodiments. Reference below is toLM CS 40 only, for convenience, but each step may be performed by eitherone or both of LM CS 40 and CM CS 10.

In step 1010, LM CS 40 receives from a scanner (either scanner 50 or aseparate scanner forming part of LM CS 40) an ID and proceeds to step1010A.

In step 1010A, LM CS 40 logs the received ID and proceeds to step 1020.For example, this logging may be addition of a record in table 600.

In step 1020, LM CS 40 determines if the ID is a voucher ID (includingfor example a return telephone code ID). This determination may be basedupon comparison to voucher ID specification or by comparison to actualvoucher IDs stored for example in Input Voucher ID field 410 in table400 and return telephone code field 510 in table 500. If thedetermination is yes, LM CS 40 proceeds to step 1020A. If thedetermination is no, LM CS 40 proceeds to step 1020B. In steps 1020A and1020B, LM CS 40 logs the step 1020 determination.

From 1020A, LM CS 40 proceeds to step 1030.

In step 1030, LM CS 40 determines whether to print a coupon. In thefirst class of implementations, there merely requires no timecorrelation determination. In the second class of embodiments, LM CS 40determines if there is a voucher ID and a product ID with which thedetermined voucher ID is already associated in memory on LM CS 40. Forexample whether such IDs were received within 30 seconds, 45 seconds, 60seconds, 90 seconds, or 120 seconds of one another. And in addition,whether those two IDs are associated with one another in memory in LM CS40, for example, residing in the same records as one another in eitherCoupon Triggering Table 400 or Coupon Triggering Table 500. If yes, LMCS 40 proceeds to step 1030A. If no, LM CS 40 proceeds to step 1030B.

In step 1030A. LM CS 40 logs the step 1030 determination and proceeds tostep 1040.

In step 1040, LM CS 40 prints a coupon associated with the determinedvoucher ID and proceeds to step 1040A. For example, the couponassociated with the coupon data in the record in Coupon Triggering Table400 or Coupon Triggering Table 500 that contains the associated and timecorrelated voucher ID and product ID.

In step 1040A, LM CS 40 logs the printing of the coupon printed in step1040 and proceeds to step 1010.

In step 1020B, LM CS 40 logs the determination in step 1020 and proceedsto step 1050.

In step 1050, LM CS 40 determines whether the ID received from scanner50 in step 1010 is a product ID. If yes, LM CS 40 proceeds to step1050A. If no, LM CS proceeds to step 1050B.

In step 1050A, LM CS 40 logs the determination in step 1050 and proceedsto step 1030.

In step 1050B, LM CS 40 logs the determination in step 1050 and proceedsto step 1060.

In step 1055, LM CS 40 determines whether the product ID triggersprinting of a voucher.

In step 1055A AND 1055 b, LM CS 40 logs the determination in step 1055.

In step 1056, LM CS 40 prints any voucher triggered by the product ID,and returns processing to 1030.

In step 1060, LM CS 40 determines whether the ID received in step 1010is a coupon ID. If yes, LM CS 40 proceeds to step 1060A. If no, LM CSproceeds to step 1060B.

In both steps 1060A and 1060B, LM CS logs the determination in step1060, and proceeds to step 1010.

FIG. 11 shows process flow 1100 for a consumer buying a targeted item.At that time, the C-Light CS (a.k.a. LM CS 40) reads the item UPC fromthe Y cable attached to the POS Handheld Scanner 50. In 1102, C-Light CSprints a voucher having unique numeric code 921924843, a bar codecorresponding to numerals 4200006200, and text stating “Save $1.00 onMarlboro Lights”. In 1103, the consumer scans the voucher in the scannerbuilt into the C-Light CS, not scanner 50 connecting to the C-Lightsystem and POS CS 30. Alternatively, the consumer enters the unique codevia the keypad of the C-Light system. In response, in 1104, LM CS 40prints a standard coupon for $1.00 on Marlboro Lights (not shown) andalso prints a voucher for another manufacturers coupon having the samebar coded numerals 4200006200 and advising the customer “Save $1.00 onMarlboro Lights”. Use of the same bar code numerals 4200006200 enablesthe C-Light CS to associate successive purchase transactions with thesame customer.

FIG. 12 shows process flow 1200. in 1201, the customer buys a targeteditem. The C-Light CS reads the product ID (also referred to as a UPC)from the Y cable attached to scanner 50. In 1202, an display (LCDdisplay) shows a “Coupon Available” message to the customer, and a legalmessage about age verification. The customer, if of age, presses an“Accept” button on the keypad of the C-Light CS. In 1203, the C-Light CSresponds by printing a voucher stating “Save $1.00 on Marlboro Lights”.In 1204, the customer scans the voucher with the scanner built into theC-Light CS or enters the unique code via the keypad of the C-Lightsystem. In 1205, in response, the C-Light CS prints a coupon stating“Save $1.00 on Marlboro Lights” and containing the same bar codednumerals 4200006200 as the voucher in step 1203.

FIG. 13 shows software interface diagram 1300 including C-Store POSregister 1301, C-Store Hand Held POS Scanner 1302, Item UPC 1303, HandHeld Scanner Service 1304, Driver Interface (SS) 1305, C-Store SystemScanner Service 1306, CMC Print Voucher 1307, CoupApp (SS) 1308, C-StoreController App (SS) 1309, C-Store PinPad Device 1311, Manual VoucherEntry 1310, Std. Print Subsystem (SS) 1312, and C-Store LCD Display1313.

In operation, a UPC) product ID) scanned by the scanner 50 in steps1302, 1303. Date therefrom flows to the POS CS 30 (1301) and to theHandheld Scanner Service 1304 in LM CS 40. LM CS 40 then responds tothat data by effecting process flow 1309, 1308, 1312, and 1313 possiblyresulting in display in LCD display of product information data in 1312and printing of a coupon in 1312.

In operation, a voucher is read by the LM CS 40's scanner in 1306, 1307,data from which is processed by LM CS 40 Driver Interface 1305, whichflows to step 1309 for determination whether to print and display acoupon and product information data.

In operation, a voucher ID may be entered in a keypad, corresponding tosteps 1310 and 1311, which data thereafter flows to LM CS 40 DriverInterface (SS) 1305, and is processed as discussed above.

One method of updating the LM CS 40 includes the local LM CS 40wirelessly connecting via the cellular telephone network to the CM CS 10and then updating its local files based upon data received from the CMCS 10. In this method, LM CS 40 preferably includes a cellular networkcard. This data comprises voucher Identifications (“IDs”),correspondence of voucher IDs to coupon offers, coupon offers, andrelated files, and updates to specifications of for bar code scanner 50,and product identifications. In one embodiment, this information wouldalso include customer cellular telephone number (or portion thereof suchas the last 4 digits) corresponded to coupons for certain products,using the cellular telephone number as an identifier.

Customer Oriented Description of the Preferred Methods of Use

As indicated above, processing is described as performed by LM CS 40,but may be distributed with CM CS 10.

In a first preferred method of use, a customer present a product forpurchase. Scanning of that product by scanner 50 results in LM CS 40printing a voucher adjacent the customer. The voucher contains writingstating that it can be presented for obtaining a coupon on one or morespecified products. The voucher contains a bar code.

The customer presents the voucher at some point in time when purchasinga product specified on the voucher. The voucher and the specifiedproduct are scanned by scanner 50.

LM CS 40 receives inputs of the identifications for the specifiedproduct and the voucher, which prompts LM CS 40 to determine whetherthey are scanned within a correlation time of one another.

If LM CS 40 determines that both items are scanned within thecorrelation time, LM CS 40 responds by printing a corresponding couponadjacent the customer's location at checkout.

The customer may then present that coupon for scanning which will resultin the POS CS reducing the sales price for the customer's order by adiscount amount specified in the coupon.

In a second preferred method of use, a customer present a product forpurchase. Scanning of that product by scanner 50 results in LM CS 40printing a voucher adjacent the customer. The voucher contains writingstating that it can be presented for obtaining a coupon on one or morespecified products. The voucher specifies a telephone number and atriggered telephone code.

The customer calls the specified telephone number and enters thetriggered telephone code.

A CS that received the triggered telephone code transmits back to thesending telephone number, typically a cellular telephone number, areturn telephone code.

The transmission back to the sending telephone number may also identifythe specified products.

When purchasing one of the specified products, the customer enters thereturn telephone code via a keypad on the LM CS 40, into LM CS 40. LM CS40 responds by examining product items scanned within a correlation timeof its receipt of the return telephone code, determining if any of thoseproducts are specified products, and if so, responds by printing acorresponding coupon.

LM CS 40 preferably also prints another voucher. Preferably, the newvoucher contains a voucher identifications and/or a triggered telephonecode that encodes the customer's cellular telephone number. As a result,the customer's subsequent use of the new voucher identifications and/ora triggered telephone code time correlated to scanning of productidentifications may be used to build a time correlation history databaseof assumed purchases over time in association with the customer'scellular telephone number.

Broad Conception of Use of Time Correlation of Product Identifications

In a broader concept of the invention, the time correlation of receiptof two identifications codes from items scanned at a scanning location,such as a POS or a point of entry of medical or medical prescriptioninformation is used to trigger transmission of consumer information,such as medical information, to a consumer related to the items beingscanned. Such information may be medical information, marketinginformation, incentive offers, vouchers, or coupons. For example, LM CS40 may be programmed to respond to input within a time correlation (say30 seconds) of two scanned product identifications for medicines knownto have harmful interactions by printing or displaying or voicing awarning message. For example, scanning of two different antiinflammatory medicines, or scanning of two anti histamines, may triggerprinting of a warning indicating that use of both medicines is contraindicated. Similarly, scanning of any two products having somerelationship there between may trigger printing of information aboutthat relationship. For example, scanning identifying milk and peanutbutter within 30 seconds of one another may trigger LM CS 40 to print amessage noting that consumption of milk and peanut butter at the sametime provides a more complete protein. This type of implementationoutputs product information data or targeted signals, which may or maynot include coupon or voucher data.

Use of time correlation avoids the requirement to receive an end oftransaction signal in order to associate a set of productidentifications within a purchase transaction, or any other type of datainput transaction, such as prescription entries and optionally relatedpurchases in a pharmacy store. As a result, systems responding to timecorrelations between entered data are feasible and cost effectivealternatives to systems that rely upon receipt from a point of entry orpoint of sale or pharmacy management system for an end of transactionsignal. For example, a retail store including plural LM CSs or one LM CSemploying plural Y cables or equivalent all communicating with the oneLM CS in a store, are feasible alternatives. Plural intelligent Y cablesor their alternatives noted above, in addition, to wired or wirelesstransmission therefrom to a single LM CS per retail store, or a numberof LM CSs that is less than the number of checkout lanes, iscontemplated. In such embodiments, voucher information printed near eachPOS would include encoded identifications of the corresponding POS orcheckout location in addition to other information noted above, in orderto also correlate the identifications scanned at that checkout locationand voucher codes, with one another.

Electronic Coupons Transmitted from LM CS 40 to POS CS 10 During theTransaction Instead of Printing Paper Coupons

In one preferred embodiment, instead of printing a coupon containing ascannable bar code, LM CS 40 outputs coupon data by transmitting thecorresponding standardized coupon identifications directly to POS CS 30via its scanner input connected to intelligent Y cable 60. Oneimplementation of this embodiment includes a variation of intelligent Ycable 60 such that intelligent Y cable 60 supports two way datacommunication to and from LM CS 40. In this implementation, intelligentY cable is configured to receive from LM CS 40 a coupon identificationand transmit that coupon identification promptly to POS CS 30. Promptly,here, means for example after completion of transmission of data for abar code scan buffered in and not yet sent from Y cable 60 to POS CS 30.As a result, the same safeguards against fraud as for printed couponsexist and in addition the customer is relieved of the requirement toreceive and have a scanned a paper coupon. Moreover, LM CS 40 may beconfigured to forward a log file containing its transmission of couponidentifications to CM CS 10 or to a coupon clearinghouse organization,which can then adjudicate accounting between the corresponding retailstore owners and coupon sponsors by the amount of the discountsindicated in the log files. A substantial benefit of this electroniccoupon embodiment is that it avoids the requirement to count papercoupons in paper coupon clearinghouses, thereby mooting substantialexpense. Any method for LM CS 40 to transmit a coupon identifications toPOS CS 30 promptly; during the ongoing purchase transaction, providesthe foregoing benefits. Thus, any mode of wireless or wired transmissionfrom LM CS 40 to POS CS 30 enabling POS CS 30 to capture the couponidentifications is envisioned. These modes include WiFi, infrared,cellular and direct network connection via a local network.

Alternative Embodiments

Several alternative and currently less preferred embodiments exists.

Instead of an intelligent Y cable, there may be connected to the outputof scanner 50 a CS having wireless transmission capability, and one orboth of the LM CS 40 and POS CS 50, and even CM CS 10, may receivewirelessly the data scanned by scanner 50. Again, preferably, the CSconnected to the output of scanner 50 is configured to filter data inthe manner described above for the Y cable.

Moreover, the devices that the customer and the store clerk use to inputand output data may vary. For example, the consumer may use theircellular telephone to communicate over a variety of standards to inputdata, such as codes, into LM CS 40, instead of using a keypad or scanner50. For example, LM CS may include a monitor to display voucher,triggered telephone code, or coupon information, to the customer.

In one alternative, the customer's cellular telephone (or wirelesspersonal digital assistant) includes a built in scanner. The consumerscans product identifications of products the consumer intends topurchase and optionally also scans a voucher, and then brings thoseitems to the POS and downloads the pre scanned information to eitherscanner 50, the CS associated with intelligent Y cable, or to LM CS 40and POS CS 50. An advantage of this process is that the customer mayalso use their device to determine what incentives to expect beforereaching checkout, while making purchase decisions. The customer may doso by communicating wirelessly with a database specifying discountsbased upon the voucher or code stored in the consumer's cellulartelephone.

In a less preferred invention, instead of filtering being performed byan intelligent Y cable, POS CS 30 is modified so that an error codegenerated by receipt of a scanned bar code not recognizable by POS CS 30does not result in POS CS 30 hanging in all error state. This can be byeither implementing an error handling routine in POS CS 30 that returnsPOS CS 30 to a state where it awaits data from scanner 50, or byreprogramming POS CS 30 to recognize and take no action processing dataassociation with codes used by LM CS 40 for vouchers.

Methods not Requiring Time Correlation

The first class of implementations do not require time correlationbetween receipt in LM CS 40 of voucher ID and product ID as aprerequisite for printing a coupon. One such method involves firsttriggering, in response to reading a Product ID, print on LM CS 40'sprinter a voucher with a voucher ID number and a corresponding bar code.LM CS 40 stores the corresponding bar code in memory in association witha coupon for a product. The customer would then have to take the printedvoucher printed by LM CS 40, and have it scanned by a scanner associatedwith both POS CS 30 and LM CS 40, or by a scanner associated only withLM CS 40. The voucher ID would be recognized in LM CS 40 and trigger theprint of a coupon. That coupon for example could be a coupon requiringpurchase a product competing with the purchased product (such as Cokefor Pepsi soda or Marlboro for Camel cigarettes). This method does notrequire time correlation. Hence, it is simpler to implement. However, itcannot limit print of a coupon to a time period in which the IDs forboth the voucher and the product for which the associated couponprovides a benefit are scanned.

A second method involves the consumer dialing a number to connect to LMCS 40 or CM CS 10 and optionally entering a specified PIN encoding atleast an identification of the retail store or LM CS 40, in order toobtain coupons. The responding CS would then send a text messagenotifying the consumer of coupons available that week to that consumer,or provide to that consumer a second PIN to enter into LM CS 40 alphakey pad to which the LM CS 40 would respond by printing the specifiedcoupons. Preferably, the second PIN would be part or all of thecustomer's cell phone number (for example the last 4 digits of thecustomer's cell phone number) or otherwise uniquely to the correspondingretail store encode the customer's cell phone number. As a result the LMCS 40 and/or CM CS 10 could obtain a CID specific to that consumer andretail store of LM CS. That CID could also be used to comply with agelimitation laws. For example, the store clerk could be instructed todetermine if the customer was of legal age, and if so, to then enter a“dummy” product ID into scanner 50 indicating whether the consumer wasof age and ring up a zero cost transaction, and the LM CS 40 wouldcapture that transaction information from the intelligent Y cable,including the “dummy” product ID indicating whether the customer was oflegal age. Alternatively, the text message may instruct the customer toenter some other data into the alpha pad on the LM CS 40 in order toobtain coupons. Alternatively, the customer's cell telephone number orother data the LM CS 40 needs in order to print coupons for thecustomer, may be transmitted by the customer from the customer's cellphone to the LM CS 40. This is in implementations where the LM CS 40includes a built in cell telephone card and telephone number.Alternatively, such transmission could be via WiFI or blue toothconnection or similar wireless standards.

In another method, the user calls a specified telephone number (for theCM CS 10 or the LM CS 40) and then receives a code corresponding to apromotional program. That code was previously sent to and stored in LMCS 40 (say, during a weekly update), from the CM CS 10. The customermust enter that code to obtain the coupon. Two drawbacks to this systemare relatively low security and that the LM CS 40 does not therebyobtain a CID (such as a cell number) for the customer.

In another method, the user receives a notification (for example by cellphone text message or verbally from the store clerk, or via a displayvisible to the customer provided by the LM CS 40) of what promotions theuser is entitled to if the user enters their CID (cell number or portionthereof) on the alpha keypad of LM CS 40. This mode has two benefits.First, LM CS 40 can read and store a CID, and in addition, it canassociate product IDs of purchased products with that CID occurringwithin a specified time period, such as 1 minute. Thus, use of aCID/cell number provides the marketing CSs the ability to obtain asubstitute for purchase history, time correlation of scanned productidentifications. Second, since a cell telephone number ID is required toobtain coupons, fraud is substantially reduced.

Related Credit Card Processing Using LM CS 40

LM CS 40 may also have a credit card reader interface so that the builtin cell telephone card can perform credit card authorization telephonecalls. Some inventive methods include features relating to credit cardauthorization and using the customer's cell telephone number as a CID,as noted below.

LM CS 40 may be used in a manner that induces retail store owners andbanks and credit card companies. These revolve around the LM CS 40having a built in cell telephone communication capability to makenetwork connections. In preferred embodiments, cellular telephonetransmission between LM CS 40 and CM CS 10 only occurs at off hours, atnight or when the corresponding retail store is closed or typically slowin sales.

One option is to offer the merchants a hookup to the cell telephone todial and perform their credit card authorizations of transactions. Thisoption would be desirable for merchants that do not want the additionalexpense and infrastructure support costs for telephone lines dedicatedfor credit card transactions. In this option, LM CS 40 is equipped witha plug and interface for accepting the standard credit card readerdevice, enabling the retail store owner to perform authorization (creditcard and bank card) via the LM CS 40's cellular telephone card.

Another option provides customers an incentive to use their creditcards, which in turn may be used to solicit marketing dollars fromcredit card companies. In addition, credit card authorization processingthrough LM CS 40 enables it to capture credit card number data, anothersource of CID, in addition to cell telephone number CIDs. That enablesthe following additional possibilities.

Since the LM CS sees cell telephone number, credit card number data, andscanned product ID data in a time correlated fashion, LM CS 40 mayassociate all of that data together to provide purchase records withoutperforming time correlation processing. LM CS 40 would then receive asinput and log for example, at least some of cell number, credit cardnumber, product ID, date/time, retail store ID, checkout lane. Thatinformation may be used for purchase history based targeted marketingand for its inherent value in analyzing convenience store sales.

The specific embodiments herein above are only exemplary, and theinventors rights should not be limited to those embodiments. The broadinventive concepts for which protection is sought are defined by theappended claims.

1. A system for building a time correlation history database: atargeting CS comprising at least one targeting CS central processingunit, at least one targeting CS memory, at least one targeting CS input,and at least one targeting CS output; wherein said at least onetargeting CS input is configured to receive at least personal deviceaddresses and product identifiers; wherein said at least one targetingCS memory comprises a time correlation log; wherein said timecorrelation log is configured to store time of receipt of each one ofsaid at least one personal device addresses in association with thecorresponding one of said personal device address, and to store time ofreceipt of each one of said product identifiers in association with thecorresponding one of said product identifiers; wherein said at least onetargeting CS memory comprises a time correlation history data structurefor storing in association with one another, at least (1) a personaldevice address, (2) a personal device address time of receipt of saidpersonal device address, and (3) one or more product identifiers eachhaving a product identifier time of receipt correlated in time with saidpersonal device address time of receipt; and wherein said targeting CSis configured to process data in said time correlation log to populatesaid time correlation history data structure by determining if time ofreceipt of a product identifier in said time correlation log is withintime of receipt a personal device address time of receipt in said timecorrelation log. 2-4. (canceled)
 5. A system for outputting productinformation data, comprising: a LM CS, said LM CS including: a LM CScentral processing unit for processing instructions and data; a LM CSmemory for storing data; at least one LM CS input for receivingidentification codes; and at least one LM CS output for outputtingidentification codes; wherein said LM CS memory stores data specifying acorrelation time; wherein said LM CS is configured to output productinformation data including a first product information identificationcode to said at least one LM CS output in response to receipt via saidat least one LM CS input of a first voucher identification code and afirst product identification code, only if, said LM CS receives saidfirst voucher identification code via said at least one LM CS input andsaid first product identification code via said at least one LM CS inputwithin said correlation time of one another. 6-33. (canceled)
 34. Asystem for outputting coupon data, comprising: a LM CS, said LM CSincluding a LM CS central processing unit for processing instructionsand data; a LM CS memory for storing data; at least one LM CS input forreceiving identification codes; and at least one LM CS output foroutputting identification codes; a POS CS; a bar code scanner forscanning bar codes; and an intelligent data router containing circuitryconfigured to transmit all scanned bar code data scanned by said barcode scanner corresponding to identification codes along a first datacommunication path coupled to said at least one LM CS input andselectively transmitting scanned bar code data along a second datacommunication path coupled to said POS CS.
 35. (canceled)
 36. A systemfor outputting coupon data, comprising: a LM CS, said LM CS including aLM CS central processing unit for processing instructions and data; a LMCS memory for storing data; at least one LM CS input for receivingidentification codes; and at least one LM CS output for outputtingidentification codes; a POS CS having a POS CS input; a bar code scannerfor scanning bar codes and coupled to said at least one LM CS input andto said POS CS input; wherein said LM CS is configured to output coupondata upon receipt from said bar code scanner of voucher identificationdata; and wherein said POS CS is configured so that, upon receipt fromsaid bar code scanner of voucher identification, said POS CS either doesnot enter an error state or executes error handler code the returns saidPOS CS to a state in which it awaits receipt of another identificationcode from said bar code scanner.
 37. A system for issuing productinformation data to a customer near an end of a customer transaction,comprising: a targeting CS comprising at least one targeting CS centralprocessing unit, at least one targeting CS memory, at least onetargeting CS input, and at least one targeting CS output; wherein saidat least one targeting CS input is configured to receive productidentifiers of product items being scanned at a POS in a retail store;wherein said at least one targeting CS memory comprises a timecorrelation log; wherein said time correlation log is configured tostore at least (1) time of receipt of each product identifier scanned atsaid POS in association with (2) the corresponding product identifier;wherein said targeting CS memory stores at least one assumed end oftransaction rule for assuming when a customer transaction at said POS isending; wherein said targeting CS is structured to determine from datain said time correlation log and said at least one assumed end oftransaction rule an assumed end of transaction time; and wherein saidsystem is configured to convey to a customer at the POS productinformation data at a time depending upon said assumed end oftransaction time. 38-43. (canceled)
 44. The system of claim 37, whereinsaid targeting CS is structured: (1) to determine whether productidentification data newly received in said targeting CS is a voucher ID,and if so, automatically retrieving from said at least one targeting CSmemory at least one associated product identifier associated with saidvoucher ID, then (2) to determine whether pre existing records in saidtime correlation log have a time of receipt within a first correlationtime of time of receipt of said voucher ID and include a productidentifier that is said associated product identifier; (3) to determinewhether product identifiers received after said time of receipt of saidvoucher ID prior to said assumed end of transaction time are saidassociated product identifier; and to print or display to said customersaid information data if (1) is positive and either (2) or (3) ispositive. 45-49. (canceled)
 50. The system of claim 5: wherein saidproduct information data is coupon data; and wherein said LM CS isconfigured to output coupon data including a first coupon identificationcode to said at least one LM CS output in response to receipt via saidat least one LM CS input of a first voucher identification code and afirst product identification code, only if, said LM CS receives saidfirst voucher identification code via said at least one LM CS input andsaid first product identification code via said at least one LM CS inputwithin said correlation time of one another.
 51. The system of claim 50wherein said LM CS configured to output coupon data further comprises:said LM CS configured to store in said LM CS memory (1) identificationcodes received via said at least one LM CS input and (2) their time ofreceipt via said at least one LM CS input in association with oneanother; and said LM CS configured to respond to receipt of a currentlyreceived identification code received via said at least one LM CS input,by (1) determining whether said currently received identification codeis said first voucher identification code, and (2) if said LM CSdetermines that said currently received identification code is saidfirst voucher identification code, determining whether time of receiptvia said at least one LM CS input of said currently receivedidentification code is within said correlation time of a time of receiptvia said at least one LM CS input of said first product identificationcode.
 52. The system of claim 51 wherein said LM CS configured to storein said LM CS memory (1) identification codes received via said at leastone LM CS input and (2) their time of receipt via said at least one LMCS input in association with one another, sequenced by time of receipt;and wherein said determining whether time of receipt via said at leastone LM CS input of said currently received identification code is withinsaid correlation time of time of receipt via said at least one LM CSinput of said first product identification code comprises: sequentiallyretrieving based upon time of receipt, identification codes received viasaid at least one LM CS input, determining whether time of receiptassociated with each retrieved identification code is not within acorrelation time of receipt of said currently received identificationcode and, when determining that time of receipt associated with aretrieved identification code is not within said correlation time,ceasing said sequentially retrieving.
 53. The system of claim 50 whereinsaid LM CS configured to output coupon data comprises: said LM CSconfigured to store in said LM CS memory (1) identification codesreceived via said at least one LM CS input and (2) their time of receiptvia said at least one LM CS input in association with one another; andsaid LM CS configured to respond to receipt of a currently receivedidentification code received via said at least one LM CS input by (1)determining whether said currently received identification code is saidfirst product identification code, and (2) if said LM CS determines thatsaid currently received identification code is said first productidentification code, determining whether time of receipt via said atleast one LM CS input of said currently received identification code iswithin said correlation time of a time of receipt via said at least oneLM CS input of said first voucher identification code.
 54. The system ofclaim 53 wherein said LM CS configured to store in said LM CS memory (1)identification codes received via said at least one LM CS input and (2)their time of receipt via said at least one LM CS input in associationwith one another, sequenced by time of receipt; and wherein saiddetermining whether time of receipt via said at least one LM CS input ofsaid currently received identification code is within said correlationtime of time of receipt via said at least one LM CS input of said firstvoucher identification code comprises: sequentially retrieving basedupon time of receipt, identification codes received via said at leastone LM CS input, determining whether time of receipt associated witheach retrieved identification code is not within a correlation time ofreceipt of said currently received identification code and, whendetermining that time of receipt associated with a retrievedidentification code is not within said correlation time, ceasing saidsequentially retrieving.
 55. The system of claim 50 wherein said LM CSis configured to output, via said at least one LM CS output, voucherdata including a voucher identification code in response to said LM CSreceiving via said at least one LM CS input a voucher triggering productidentification code.
 56. The system of claim 55 wherein said vouchertriggering product identification code is said first productidentification code.
 57. The system of claim 55: wherein said LM CSmemory stores a voucher output triggering lookup table, and said voucheroutput triggering lookup table stores in association with each voucheridentification code at least one product identification code; whereinsaid LM CS is configured to, in response to receipt of a receivedproduct identification code, look up in said voucher triggering lookuptable whether said received product identification code is associatedwith said first voucher identification code, and, if said LM CSdetermines that said received product identification code is associatedwith said first voucher identification code, outputting to at least oneof said at least one LM CS output, outputted voucher data correspondingto said first voucher identification code.
 58. The system of clam 57wherein said outputted voucher data includes said first voucheridentification code.
 59. The system of claim 57: wherein said outputtedvoucher data is stored in a data structure in a certain CS memory of acertain CS in association with said first voucher identification code;and wherein said certain CS is configured to receive via a certain CSinput said outputted voucher data in association with a transmittingcellular telephone number from which said outputted voucher datacorresponding to said first voucher identification code was transmitted,and to transmit via a certain CS output to said transmitting cellulartelephone number said first voucher identification code.
 60. The systemof claim 59 further comprising a wireless electronic transmission devicehaving said transmitting cellular telephone number.
 61. The system ofclaim 59 wherein said certain CS is said LM CS.
 62. The system of claim59 wherein said certain CS is a CM CS including a CM CS centralprocessing unit, a CM CS memory, at least one CM CS input for inputtingdata, and at least one CM CS output for outputting data.
 63. The systemof claim 59 wherein said certain CS is configured to store inassociation with one another cellular telephone numbers and productidentifications in a time correlation history database; and said timecorrelation history database stores said transmitting cellular telephonenumber in association with product identifications for products having atime of receipt in said LM CS within a second correlation time of timeof receipt via said certain CS input of a telephone transmission fromsaid transmitting cellular telephone number.
 64. The system of claim 59wherein said time correlation history database also stores inassociation with each product identification a product identificationtime of receipt via said at least one LM CS input or said certain CSinput.
 65. The system of claim 64 wherein said product identificationtime of receipt corresponds to one of time of receipt of a cellulartelephone signal in said certain CS, time of receipt of a productidentification in said LM CS, and time of receipt of a productidentification in said certain CS.
 66. The system of claim 50 whereinsaid at least one LM CS input for receiving identification codescomprises a scanner for reading bar codes.
 67. The system of claim 66further comprising an intelligent data router containing circuitryconfigured to transmit all scanned bar code data scanned by said scannercorresponding to identification codes along a first data communicationpath coupled to said at least one LM CS input and selectivelytransmitting scanned bar code data along a second data communicationpath.
 68. The system of claim 67 wherein said circuitry blockstransmission of voucher identification codes along said second datacommunication path.
 69. The system of claim 66 wherein said intelligentrouter forms part of an intelligent Y cable connecting said scanner tosaid LM CS.
 70. The system of claim 66 further comprising a POS CS, afirst data communication path from said scanner to said at least one LMCS input, and a second data communication path from said scanner to aninput of said POS CS, and wherein said POS CS is configured so thattransmission of data from said scanner to said input of said POS CS doesnot result in an error condition in said POS CS.
 71. The system of claim66 further comprising a POS CS, a first data communication path fromsaid scanner to said at least one LM CS input, and a second datacommunication path from said scanner to an input of said POS CS, andwherein said POS CS is configured so that transmission of a voucheridentification code from said scanner to said input of said POS CSresults in activation of error code in said POS CS that returns said POSCS to a state in which it awaits receipt of another identification codefrom said scanner.
 72. The system of claim 50 wherein said at least oneLM CS input for receiving identification codes comprises a key padhaving numerals 0 through 9 for entering voucher identification codes indecimal format.
 73. The system of claim 72 wherein said at least one LMCS input for receiving identification codes comprises a scanner.
 74. Thesystem of claim 50: wherein said at least one LM CS output comprises aprinter; wherein said printer is configured to print a coupon containinga bar code specifying said first coupon identification code in responseto receipt by said printer of coupon data including said first couponidentification code.
 75. The system of claim 50: wherein said at leastone LM CS output comprises at least one of a printer, a monitor, and awireless transmitter; and wherein said at least one of said printer,said monitor; and said wireless transmitter are configured to output atleast one of machine and human readable versions of said first couponidentification code.
 76. The system of claim 50 wherein said coupon dataincluding said first coupon identification code output to said at leastone LM CS output includes identification of at least one product forwhich a coupon having said first coupon identification code can beredeemed.
 77. The system of claim 50 wherein said correlation time isbetween 30 seconds and 2 minutes.
 78. The system of claim 34 whereinsaid circuitry blocks transmission of voucher identification codes alongsaid second data communication path.
 79. The system of claim 37 whereinsaid product information data is a voucher ID and said customertransaction is a purchase transaction.
 80. The system of claim 37wherein said product information data is voucher ID, and said system isconfigured to display the existence of a voucher and to print thevoucher containing said voucher ID, either in response to, or at aspecified time after, said assumed end of transaction time.
 81. Thesystem of claim 37 wherein said at least one assumed end of transactionrule comprises a first time interval.
 82. The system of claim 37 whereinsaid at least one assumed end of transaction rule comprises a first timeinterval and said rule specifies an assumed end of transaction when saidfirst time interval elapses with no codes received by said at least onetargeting CS input.
 83. The system of claim 37 wherein said at least oneassumed end of transaction rule comprises a second time interval. 84.The system of claim 83 wherein said at least one assumed end oftransaction rule comprises association of a set of at least two productsIDs received by said at least one targeting CS input within said secondtime interval of one another.